Method, system, and terminal device for transmitting information

ABSTRACT

Methods, systems, and terminal devices for transmitting information are provided. An exemplary system includes a sending end and at least one receiving end. The sending end is configured to obtain audio data to be transmitted, encode the obtained audio data according to an M-bit unit length, and use a pre-set cross-platform audio interface to control an audio outputting device of the sending end to send the encoded audio data to the at least one receiving end. The M-bit unit length is an encoding length corresponding to each frequency of a number N of frequencies, N is greater than or equal to 2, and M is greater than 0. The at least one receiving end is configured to use the pre-set cross-platform audio interface to control an audio inputting device of the at least one receiving end to receive the encoded audio data.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation application of PCT Patent ApplicationNo. PCT/CN2014/077779, filed on May 19, 2014, which claims priority toChinese Patent Application No. CN201310222406X, filed on Jun. 6, 2013,the entire contents of which are incorporated herein by reference.

FIELD OF THE DISCLOSURE

The present disclosure relates to the field of communication technologyand, more particularly, relates to methods, systems, and terminaldevices for transmitting information.

BACKGROUND

Currently, wireless communication technology uses electromagnetic fieldsemitted from a terminal device to transmit information. This has higherhardware requirements for the terminal device.

For example, Bluetooth wireless transmission can be used and requiresboth a sending end and a receiving end to be equipped with Bluetoothcommunication modules. Information can then be transmitted, after asuccessful pairing of the communication parties.

For WIFI wireless transmission, the sending end and the receiving endare also required to be equipped with WIFI communication modules. Thecommunication parties have to be successfully paired before informationcan be transmitted.

BRIEF SUMMARY OF THE DISCLOSURE

One aspect of the present disclosure includes an informationtransmitting method implemented by a system including a sending end andat least one receiving end. The sending end obtains audio data to betransmitted, encodes the obtained audio data according to an M-bit unitlength and uses a pre-set cross-platform audio interface to control anaudio outputting device of the sending end to send the encoded audiodata to the at least one receiving end. The M-bit unit length is anencoding length corresponding to each frequency of a number N offrequencies, N is greater than or equal to 2, and M is greater than 0.The at least one receiving end uses the pre-set cross-platform audiointerface to control an audio inputting device of the at least onereceiving end to receive the encoded audio data.

Another aspect of the present disclosure includes an informationtransmitting method implemented by a sending end containing an audiooutputting device by obtaining audio data to be transmitted, encodingthe obtained audio data according to an M-bit unit length, and using apre-set cross-platform audio interface to control the audio outputtingdevice of the sending end to send the encoded audio data to at least onereceiving end, such that the at least one receiving end uses the pre-setcross-platform audio interface to control the audio inputting device atthe at least one receiving end to receive the encoded audio data. TheM-bit unit length is an encoding length corresponding to each frequencyof a number N of frequencies, N is greater than or equal to 2, and M isgreater than 0.

Another aspect of the present disclosure includes an informationtransmitting method, implemented by a receiving end containing an audioinputting device. A pre-set cross-platform audio interface is used tocontrol the audio inputting device of the receiving end to receiveencoded audio data sent from an audio outputting device of a sending endby a processing including: using the pre-set cross-platform audiointerface to create a new thread, using the new thread to control theaudio inputting device of the receiving end to receive the encoded audiodata, wherein the encoded audio data include audio data having appendedtags at a start position and an end position of the audio data,converting the received audio data into an audio signal via fast Fouriertransform, restoring the audio signal to a digital signal according to adigital frequency encoding table, and using the third-party library todecode the digital signal and to obtain audio data to be transmitted.

Another aspect of the present disclosure includes an informationtransmitting system. The system include a sending end and at least onereceiving end, the sending end containing an audio outputting device andthe at least one receiving end containing an audio inputting device. Thesending end is configured to obtain audio data to be transmitted, toencode the obtained audio data according to an M-bit unit length, and touse a pre-set cross-platform audio interface to control the audiooutputting device to send the encoded audio data to the at least onereceiving end. The M-bit unit length is an encoding length correspondingto each frequency of a number N of frequencies, N is greater than orequal to 2, and M is greater than 0. The at least one receiving end isconfigured to use the pre-set cross-platform audio interface to controlthe audio inputting device of the at least one receiving end to receivethe encoded audio data.

Another aspect of the present disclosure includes a terminal devicecontaining an audio outputting device. The terminal device includes adata obtaining unit, a data encoding unit, and a data sending unit. Thedata obtaining unit is configured to obtain audio data to betransmitted. The data encoding unit is configured to encode the obtainedaudio data according to an M-bit unit length. The M-bit unit length isan encoding length corresponding to each frequency of a number N offrequencies, N is greater than or equal to 2, and M is greater than 0.The data sending unit is configured to use a pre-set cross-platformaudio interface to control the audio outputting device of the sendingend to send the encoded audio data to at least one receiving end, suchthat the at least one receiving end uses the pre-set cross-platformaudio interface to control the audio inputting device at the at leastone receiving end to receive the encoded audio data.

Another aspect of the present disclosure includes a terminal devicecontaining an audio inputting device. The terminal device includes adata receiving unit configured to use a pre-set cross-platform audiointerface to control the audio inputting device of the receiving end toreceive encoded audio data sent from the audio outputting device of thesending end.

Other aspects or embodiments of the present disclosure can be understoodby those skilled in the art in light of the description, the claims, andthe drawings of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The following drawings are merely examples for illustrative purposesaccording to various disclosed embodiments and are not intended to limitthe scope of the present disclosure.

FIG. 1 is a network architecture illustrating an exemplary system fortransmitting information in accordance with various disclosedembodiments;

FIG. 2 is a schematic illustrating an interactive process for anexemplary method for transmitting information in accordance with variousdisclosed embodiments;

FIG. 3 is a schematic illustrating an exemplary method for transmittinginformation in accordance with various disclosed embodiments;

FIG. 4 is a schematic illustrating an exemplary method for transmittinginformation in accordance with various disclosed embodiments;

FIG. 5 is a schematic illustrating an exemplary terminal device inaccordance with various disclosed embodiments;

FIG. 6 is a schematic illustrating another exemplary terminal device inaccordance with various disclosed embodiments; and

FIG. 7 is a schematic illustrating an exemplary terminal device inaccordance with various disclosed embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to exemplary embodiments of thedisclosure, which are illustrated in the accompanying drawings. Whereverpossible, the same reference numbers will be used throughout thedrawings to refer to the same or like parts.

FIG. 1 shows an exemplary information transmitting system 00. Theexemplary information transmitting system 00 can at least include asending end 1 and at least one receiving end 2. The sending end 1 iscommunicated with the at least one receiving end 2 via an acousticcommunication connection.

The sending end 1 can be any terminal device containing an audiooutputting device 11. The at least one receiving end 2 can be anyterminal device containing an audio inputting device 21. The terminaldevice can include, but be not limited to, a mobile phone, tabletcomputer, and laptop. The audio inputting device can include, but be notlimited to, a microphone. The audio outputting device can include, butbe not limited to, a speaker.

In various embodiments, the sending end obtains audio data to betransmitted, encodes the obtained audio data according to an M-bit unitlength, uses the pre-set cross-platform audio interface to control theaudio outputting device 11 to send the encoded audio data to the atleast one receiving end 2. The M-bit unit length can be a encode lengthcorresponding to each frequency of selected number N of frequencies,where N is greater than or equal to 2, and M is greater than 0. The atleast one receiving end 2 uses the pre-set cross-platform audiointerface to control the audio inputting device 21 of the receiving endto receive the encoded audio data. The obtained audio data to betransmitted can be audio data pre-stored by the sending end 1 or audiodata collected by the audio inputting device 12 of the sending end 1.The obtained audio data to be transmitted can further be audio dataconverted from text messages. The text messages can include text messageinputted by the user or text message pre-stored by the sending end 1.

In some embodiments, the sending end 1 encoding the obtained audio dataaccording to the M-bit unit length may include: selecting the number Nof frequencies in the transmittable audio frequency domain. Eachfrequency of the number N of frequencies corresponds to an M-bit encode.N is greater than or equal to 2, for example, N is 31. M is greater than0, for example, M is 5. A different tag can be appended respectively ata start position and an end position of the obtained audio data. Thedifferent tag includes a encode corresponding to any frequency of thenumber N of frequencies.

The third-party library can be used to perform an error correction tothe audio data having the appended tags. The audio data after the errorcorrection can be encoded according to the M-bit unit length. Thethird-party library can be a soloman library.

Because of the introduction of the third-party library, when the audiodata is interfered by environmental noises, the audio data can beperformed by error correction to remove the noises and to ensure thatthe audio data can be accurately and inerrably sent to the receiving endand.

The sending end 1 controls the audio outputting device 11 of the sendingend 1 and sends the encoded audio data to at least one receiving end 2via the pre-set cross-platform audio interface. This process caninclude: the sending end 1 obtains information of the at least onereceiving end 2 via the pre-set cross-platform audio interface, theinformation including, but not limited to, audio sampling information,number of channels, bits per channel, cache size of audio data, and/orbuffer size of audio data of the receiving end 2. The audio outputtingdevice 11 of the sending end 1 can be used to send current, encodedaudio data to the at least one receiving end 2, according to theobtained information of the receiving end 1. For example, each time theM-bit unit length audio data can be sent.

After finishing sending the current, encoded audio data, the callbackfunction of the cross-platform audio interface can be used to detectwhether new, encoded audio data exist. When detecting that the new,encoded audio data exist, the audio outputting device 11 of the sendingend 1 can be continuously used to send the new, encoded audio data. Whendetecting that the new, encoded audio data do not exist, the new,encoded audio data is stopped to be sent.

In addition, the controlling of the audio inputting device 21 of thereceiving end 2 to receive the encoded audio data via the pre-setcross-platform audio interface by the at least one receiving end 2includes: using the pre-set cross-platform audio interface to create thenew thread by the at least one receiving end 2; using the new thread tocontrol the audio inputting device 21 of the receiving end to receivethe encoded audio data, wherein the encoded audio data include the audiodata having the appended tags at the start position and the endposition; converting the received audio data into an audio signal viafast Fourier transform; restoring the audio signal to a digital signalaccording to a digital frequency encoding table; and/or using thethird-party library (e.g. the soloman library) to decode the digitalsignal and to obtain the audio data to be transmitted. The audio data tobe transmitted is the firstly obtained audio data to be transmitted bythe sending end.

As disclosed, a cross-platform audio interface can be configured and canbe used to block/remove differences among information transmittingplatforms of various terminal devices. Unitive standards can be used torealize information transmitting between different terminal devices.

In an exemplary scenario, the sending end includes a microphone and aspeaker, while the receiving end includes the microphone and thespeaker. The sending end records the user voice information via themicrophone, while the sending end encodes the voice information usingthe above-mentioned coding scheme, and performs the error correctionusing the soloman library during the encoding process. The sending endcontrols the speaker of the sending end to send the encoded voiceinformation via the cross-platform audio interface to multiple receivingends. The multiple receiving ends control the microphones of thereceiving ends to record the voice information via the cross-platformaudio interface. The multiple receiving ends decode the voiceinformation using the above-mentioned coding scheme, and perform theerror correction using the soloman library during the encoding processagain. The multi receiving ends broadcast the decoded voice informationvia the speakers.

Note that the above exemplary scenario only provides one example forexplanation and is not used to limit the scope of the presentdisclosure. For convenience of description, the system of FIG. 1, onlythe sending side and the receiving side are described, other componentsand elements can be included as desired. It should be clear to skilledperson in the art, the system configuration including a sending end andthe receiving end does not limit the scope of the exemplary system inFIG. 1. The sending end and the receiving end illustrated may includemore or less components, or a combination of some of the components, ora different arrangement of components. For example, the sending end andthe receiving end may include audio inputting devices and audiooutputting devices.

FIG. 2 depicts another exemplary method for information transmitting.

In Step S201, a sending end obtains audio data to be transmitted. Invarious embodiments, the obtained audio data to be transmitted can beaudio data pre-stored by the sending end or audio data collected by theaudio inputting device of the sending end, and can further be audio dataconverted from the text messages. The text messages can be text messageinputted by the user or pre-stored by the sending end. The audioinputting device includes, but is not limited to, microphone. The audiodata can include voice information inputted by the user via microphoneor other audio inputting devices.

In Step S202, the sending end encodes the obtained audio data accordingto the M-bit unit length. The M-bit unit length is an encoding lengthcorresponding to each frequency of a number N of frequencies, N isgreater than or equal to 2, and M is greater than 0.

For example, the number N of frequencies can be selected in thetransmittable audio frequency domain. Each frequency of the number N offrequencies corresponds to an M-bit encode. N is greater than or equalto 2, for example, N is 31. M is greater than 0, for example, M is 5. Adifferent tag can be appended respectively at a start position and anend position of the obtained audio data. The different tag includes aencode corresponding to any frequency of the number N of frequencies.

The third-party library can be used to perform an error correction tothe audio data having the appended tags. The audio data after the errorcorrection can be encoded according to the M-bit unit length. Thethird-party library can be a soloman library.

Because of the introduction of the third-party library, when the audiodata is interfered by environmental noises, the audio data can beperformed by error correction to remove the noises and to ensure thatthe audio data can be accurately and inerrably sent to the receiving endand.

In Step S203, the sending end controls the audio outputting device ofthe sending end and sends the encoded audio data to at least onereceiving end via the pre-set cross-platform audio interface.

In one embodiment, that the sending end controls the audio outputtingdevice of the sending end and sends the encoded audio data to at leastone receiving end via the pre-set cross-platform audio interfaceincludes: the sending end obtains information of the at least onereceiving end via the pre-set cross-platform audio interface. Theinformation includes, but is not limited to, audio sampling information,number of channels, bits per channel, cache size of audio data, and/orbuffer size of audio data of the receiving end.

The audio outputting device of the sending end can be used to sendcurrent, encoded audio data to the at least one receiving end, accordingto the obtained information of the receiving end. For example, eachtime, the M-bit unit length audio data can be sent.

After finishing sending the current, encoded audio data, the callbackfunction of the cross-platform audio interface can be used to detectwhether new, encoded audio data exist. When detecting that the new,encoded audio data exist, the audio outputting device 11 of the sendingend 1 can be continuously used to send the new, encoded audio data. Whendetecting that the new, encoded audio data do not exist, the new,encoded audio data is stopped to be sent.

In Step S204, the at least one receiving end controls the audioinputting device of the receiving end to receive the encoded audio datavia the pre-set cross-platform audio interface.

For example, that the at least one receiving end controls the audioinputting device of the receiving end to receive the encoded audio datavia the pre-set cross-platform audio interface, includes: using thepre-set cross-platform audio interface to create the new thread by theat least one receiving end; using the new thread to control the audioinputting device of the receiving end to receive the encoded audio data,the encoded audio data including the audio data having the appended tagsat the start position and the end position; converting the receivedaudio data into an audio signal via fast Fourier transform; restoringthe audio signal to a digital signal according to a digital frequencyencoding table; and/or using the third-party library (e.g. a solomanlibrary) to decode the digital signal and to obtain the audio data to betransmitted.

As disclosed, a cross-platform audio interface can be configured and canbe used to block/remove differences among information transmittingplatforms of various terminal devices. Unitive standards can be used torealize information transmitting between different terminal devices.

In one embodiment, a cross-platform audio interface as designed and theoutcome of the design can be shown as following.

#ifndef _UFO_PLATFORM_AUDIO_(—) #define _UFO_PLATFORM_AUDIO_(—) typedefstruct tagAudioDesc//### description of creating audio device { intsampleRate;//### sampling rate of audio data int channels;//### numberof channels int bitsPerChannel;//### bits per channel intbufferSize;//### buffer size of audio data int bufferCount;//### buffercount of audio data }AudioDesc; typedef struct tagAudioBufferDesc//###description of buffer block of audio data { int capacity;//### intdataSize;//### void *data;//### }AudioBufferDesc; typedef struct_OUTPUT_AUDIO//### output audio handle { int unused; }*OUTPUT_AUDIO;typedef struct _INPUT_AUDIO//### input audio handle { int unused;}*INPUT_AUDIO; //### callback function of audio playback/output typedefvoid (*AUDIO_OUTPUT_CALLBACK)(OUTPUT_AUDIO handle, AudioBufferDesc*buffer, void* userdata);//### buffer play Finish, callback //###callback function of audio input typedef void(*AUDIO_INPUT_CALLBACK)(INPUT_AUDIO handle, AudioBufferDesc *buffer,void* userdata);//### buffer record Finish, callback //### create outputaudio device OUTPUT_AUDIO ufoAudioOutputCreate(AudioDesc *desc,AUDIO_OUTPUT_CALLBACK callback, void *userdata); //### play audio intufoAudioOutputPlay(OUTPUT_AUDIO handle); //### stop outputting audio intufoAudioOutputStop(OUTPUT_AUDIO handle); //### create input audio deviceINPUT_AUDIO ufoAudioInputCreate(AudioDesc *desc, AUDIO_INPUT_CALLBACKcallback, void *userdata); //### input audio intufoAudioInputStart(INPUT_AUDIO handle); //### stop inputting audio intufoAudioInputStop(INPUT_AUDIO handle); #endif

As disclosed, the communication parties can achieve a low-cost,cross-platform, and/or cross-terminal near-field wireless communication.

FIG. 3 depicts another exemplary method for transmitting information.The exemplary method can be implemented by a sending end 1 as shown inFIG. 1. The sending end 1 can contain an audio outputting device 11.

In Step S301, audio data to be transmitted can be obtained.

In Step S302, the sending end encodes the obtained audio data accordingto the M-bit unit length. The M-bit unit length is an encoding lengthcorresponding to each frequency of a number N of frequencies, N isgreater than or equal to 2, and M is greater than 0.

For example, the number N of frequencies can be selected in thetransmittable audio frequency domain. Each frequency of the number N offrequencies corresponds to an M-bit encode. N is greater than or equalto 2, for example, N is 31. M is greater than 0, for example, M is 5.

A different tag can be appended respectively at a start position and anend position of the obtained audio data. The different tag includes aencode corresponding to any frequency of the number N of frequencies.

The third-party library can be used to perform an error correction tothe audio data having the appended tags. The audio data after the errorcorrection can be encoded according to the M-bit unit length. Thethird-party library can be a soloman library.

In Step S303, the audio outputting device is controlled to send theencoded audio data to at least one receiving end via the pre-setcross-platform audio interface, such that the at least one receiving endcontrols the audio inputting device of the receiving end and receivesthe encoded audio data via the pre-set cross-platform audio interface.

In one embodiment, the controlling of the audio outputting device tosend the encoded audio data to at least one receiving end via thepre-set cross-platform audio interface includes: obtaining informationof the at least one receiving end via the pre-set cross-platform audiointerface; using the audio outputting device to send current, encodedaudio data to the at least one receiving end, according to the obtainedinformation of the receiving end; after finishing sending the current,encoded audio data, using the callback function of the cross-platformaudio interface to detect whether new, encoded audio data exist; andwhen detecting that the new, encoded audio data exist, continuouslyusing the audio outputting device of the sending end to send the new,encoded audio data; or when detecting that the new, encoded audio datado not exist, stopping sending the new, encoded audio data.

FIG. 4 depicts another exemplary method for transmitting information.The exemplary method can be implemented by a receiving end 2 as shown inFIG. 1. The receiving end 1 can contain an audio inputting device 21.

In Step S401, a pre-set cross-platform audio interface is used tocontrol the audio inputting device of the receiving end to receiveencoded audio data sent from the audio outputting device of the sendingend.

In one embodiment, that the pre-set cross-platform audio interface isused to control the audio inputting device of the receiving end toreceive encoded audio data sent from the audio outputting device of thesending end, includes: using the pre-set cross-platform audio interfaceto create the new thread; using the new thread to control the audioinputting device of the receiving end to receive the encoded audio data,wherein the encoded audio data include audio data having appended tagsat the start position and the end position of the audio data; convertingthe received audio data into an audio signal via fast Fourier transform;restoring the audio signal to a digital signal according to a digitalfrequency encoding table; and/or using the third-party library to decodethe digital signal and to obtain audio data to be transmitted.

FIG. 5 depicts an exemplary terminal device in accordance with variousdisclosed embodiments. The exemplary terminal can be used in theexemplary system shown in FIG. 1 and can be used as a receiving end. Theexemplary terminal device can include a data obtaining unit 51, a dataencoding unit 52 and/or a data sending unit 53.

The data obtaining unit 51 is configured to obtain audio data to betransmitted.

The data encoding unit 52 is configured to encode the obtained audiodata by the obtaining unit 51 according to an M-bit unit length. TheM-bit unit length is an encoding length corresponding to each frequencyof a number N of frequencies, N is greater than or equal to 2, and M isgreater than 0.

The data sending unit 53 is configured to use the pre-set cross-platformaudio interface to control the audio outputting device of the sendingend to send the encoded audio data to at least one receiving end, suchthat the at least one receiving end uses the pre-set cross-platformaudio interface to control the audio inputting device at the at leastone receiving end to receive the encoded audio data.

In addition, the data encoding unit 52 further includes: a frequencyselecting module 521, a tag appending module 522, and/or a data encodingmodule 523.

The frequency selecting module 521 is configured to select the number Nof frequencies in the transmittable audio frequency domain. Eachfrequency of the number N of frequencies corresponds to an M-bit encode.

The tag appending module 522 is configured to append a different tagrespectively at a start position and an end position of the obtainedaudio data. The different tag can include a encode corresponding to anyfrequency of the number N of frequencies.

The data encoding module 523 is configured to use a third-party libraryto perform an error correction to the audio data having the appendedtags, and to encode the audio data after error correction according tothe M-bit unit length.

The data sending unit 53 includes: an information obtaining module 531,a data sending module 532, a detecting module 533, and/or a processingmodule 534.

The information obtaining module 531 is configured to obtain informationof the at least one receiving end via the pre-set cross-platform audiointerface.

The data sending module 532 is configured to use the audio outputtingdevice to send current, encoded audio data to the at least one receivingend according to the obtained information of the at least one receivingend.

The detecting module 533 is configured, after finishing sending thecurrent, encoded audio data, to use a callback function of thecross-platform audio interface to detect whether new, encoded audio dataexist.

The processing module 534 is configured, when detecting that the newencoded audio data exist, to continuously use the audio outputtingdevice of the sending end to send the new, encoded audio data; or whenthe new encoded audio data do not exist, to stop sending the new,encoded audio data.

FIG. 6 depicts an exemplary terminal device in accordance with variousdisclosed embodiments. The terminal device can be used in the systemaccording to FIG. 1 and can be used as a receiving end shown in FIG. 1.

The exemplary terminal device can include a data receiving unit 61. Thedata receiving unit 61 is configured to use the pre-set cross-platformaudio interface to control the audio inputting device of the receivingend to receive encoded audio data sent from the audio outputting deviceof the sending end.

The data receiving unit 61 further includes: a thread creating module611, a data receiving module 612, a converting module 613, a restoringmodule 614, and/or a data obtaining module 615.

The thread creating module 611 is configured to use the pre-setcross-platform audio interface to create a new thread.

The data receiving module 612 is configured to use the new thread tocontrol the audio inputting device of the receiving end to receive theencoded audio data. The encoded audio data include audio data havingappended tags at the start position and the end position of the audiodata.

The converting module 613 is configured to convert the received audiodata into an audio signal via fast Fourier transform.

The restoring module 614 is configured to restore the audio signal to adigital signal according to a digital frequency encoding table.

The data obtaining module 615 is configured to use the third-partylibrary to decode the digital signal and to obtain audio data to betransmitted.

The exemplary user terminal can include a mobile phone, a tabletcomputer, a PDA (personal digital assistant), a POS (point of sales), acar-carrying-computer, or any desired terminal devices. FIG. 7 depictsat least a portion of an exemplary user terminal.

As shown in FIG. 7, the exemplary terminal 700 can include an RF (RadioFrequency) circuitry 710, a storage device 720 including one or morecomputer-readable storage media, an inputting unit 730, a displayingunit 740, a sensor 750, an audio circuit 760, a transmitting module 770,a processor 780 including one or more processing cores, a power supply790, and/or other components. In various embodiments, the terminal(s)described herein can include more or less components as depicted in FIG.7. Certain parts can be omitted, combined, re-placed, and added.

The RF circuitry 710 may be used to send and receive information or sendand receive signal during communication. In particular, after receivingdownlink information from a base station, such information can beprocessed by the one or more processors 780. Further, the data relatedto the uplink can be sent to the base station. Generally, the RFcircuitry 710 can include, but be not limited to, an antenna, at leastone amplifier, a tuner, one or more oscillators, user identity module(SIM) card, a transceiver, a coupler, LNA (i.e., Low Noise Amplifier),duplexer, etc. In addition, the RF circuitry 710 may communicate withother devices via a wireless communication network. The wirelesscommunication may use any communication standards or protocols,including but not limited to, GSM (Global System for MobileCommunications), GPRS (General Packet Radio Service), CDMA (CodeDivision Multiple Access), WCDMA (Wideband encode Division MultipleAccess), LTE (Long Term Evolution), e-mail, SMS (Short MessagingService), etc.

The storage device 720 can be used for storing software programs andmodules, such as those software programs and modules corresponding tothe terminal and the third party service provider as described in FIGS.3-5 for business processing. By running software programs and modulesstored in the storage device 720, the processor 780 can perform variousfunctional applications and data processing to achieve businessprocessing. The storage device 720 can include a program storage areaand a data storage area. The program storage area can store theoperating system, applications (such as sound playback, image playback,etc.) required by at least one function. The data storage area can storedata (such as audio data, phone book, etc.) created when using theterminal. In addition, the storage device 720 may include a high-speedrandom access memory, a non-volatile memory, such as at least one diskmemory, flash memory, and/or other volatile solid-state memory elements.Accordingly, the storage device 720 may further include a memorycontroller to provide the processor 780 and the inputting unit 730 withaccess to the storage device 720.

The inputting unit 730 can be used to receive inputted numeric orcharacter information, and to generate signal input of keyboard, mouse,joystick, and trackball or optical signal input related to the usersettings and function controls. Specifically, the inputting unit 730 mayinclude a touch control panel 731 and other inputting device(s) 732. Thetouch-sensitive surface 731, also known as a touch screen or touchpanel, may collect touch operations that a user conducts on or near thetouch-sensitive surface 731. For example, a user may use a finger, astylus, and any other suitable object or attachment on thetouch-sensitive surface 731 or on an area near the touch-sensitivesurface 731. The touch-sensitive surface 731 may drive a connectingdevice based on a preset program. Optionally, the touch control panel731 may include a touch detection device and a touch controller. Thetouch detection device can detect user's touch position and detect asignal due to a touch operation and send the signal to the touchcontroller. The touch controller can receive touch information from thetouch detection device, convert the touch information into contactcoordinates to send to the processor 780, and receive commands sent fromthe processor 780 to execute. Furthermore, the touch control panel 731can be realized by resistive, capacitive, infrared surface acousticwave, and/or other types of surface touch. In addition to the touchcontrol panel 731, the inputting unit 730 may also include otherinputting device(s) 732. Specifically, the other inputting device(s) 732may include, but be not limited to, a physical keyboard, function keys(such as volume control buttons, switch buttons, etc.), a trackball, amouse, an operating lever, or combinations thereof.

The displaying unit 740 can be used to display information inputted bythe user, information provided to the user, and a variety of graphicaluser interfaces of the terminal 700. These graphical user interfaces canbe formed by images, text, icons, videos, and/or any combinationsthereof. The displaying unit 740 may include a displaying panel 741configured by, e.g., LCD (Liquid Crystal Display), OLED (OrganicLight-Emitting Diode), etc. Further, the touch control panel 731 maycover the displaying panel 741. When the touch control panel 731 detectsa touch operation on or near the touch sensitive surface, the touchoperation can be sent to the processor 780 to determine a type of thetouch operation. Accordingly, the processor 780 can provide visualoutput on the displaying panel 741. Although in FIG. 7 thetouch-sensitive surface 731 and the displaying panel 741 are shown astwo separate components to achieve input and output functions, in someembodiments, the touch control panel 731 and the displaying panel 741can be integrated to perform input and output functions.

The terminal 700 in FIG. 7 may further include at least one sensor 750,such as optical sensors, motion sensors, and other suitable sensors.Specifically, the optical sensors may include an ambient optical sensorand a proximity sensor. The ambient optical sensor may adjust brightnessof the displaying panel 741 according to the brightness of ambientlight. The proximity sensor can turn off the displaying panel 741 and/orturn backlighting, when the terminal 700 moves to an ear. As a type ofmotion sensor, a gravity sensor may detect amount of an acceleration ineach direction (e.g., including three axis) and detect magnitude anddirection of gravity when in stationary. The gravity sensor can be usedto identify phone posture (for example, switching between horizontal andvertical screens, related games, magnetometer calibration posture,etc.), vibration recognition related functions (e.g., pedometer,percussion, etc.), etc. The terminal 700 can also be configured with,e.g., a gyroscope, a barometer, a hygrometer, a thermometer, an infraredsensor, and/or other sensors.

The audio circuit 760 can include an audio inputting device 761 such asa microphone and an audio outputting device 762 such as a speaker andcan provide an audio interface between the user and terminal 700. Theaudio circuit 760 may transmit an electrical signal converted from thereceived audio data to the speaker 761 to convert into audio signaloutput. On the other hand, the microphone 762 can convert the collectedsound signal to an electrical signal, which can be received by the audiocircuit 760 to convert into audio data. The audio data can be output tothe processor 780 for processing and then use the RF circuitry 710 totransmit to, e.g., another terminal. Alternatively, the audio data canbe output to the storage device 720 for further processing. The audiocircuitry 760 may also include an earplug jack to provide communicationsbetween the peripheral headset and the terminal 700.

The terminal 700 may use the transmitting module 770 to help users sendand receive emails, browse websites, access streaming media, etc. Thetransmitting module 770 can provide users with a wireless or wiredbroadband Internet access. In various embodiments, the transport module770 can be configured within or outside of the terminal 700 as depictedin FIG. 7.

The processor 780 can be a control center of the terminal 700: using avariety of interfaces and circuits to connect various parts, e.g.,throughout a mobile phone; running or executing software programs and/ormodules stored in the storage device 720; calling the stored data in thestorage device 720; and/or performing various functions and dataprocessing of the terminal 700 to monitor the overall mobile phone.Optionally, the processor 780 may include one or more processing cores.In an exemplary embodiment, the processor 780 may integrate applicationprocessor with modulation and demodulation processor. The applicationprocessor is mainly used to process operating system, user interface,and applications. The modulation and demodulation processor is mainlyused to deal with wireless communications. In various embodiments, themodulation and demodulation processor may or may not be integrated intothe processor 780.

The terminal 700 may further include a power supply 790 (such as abattery) to power various components of the terminal. In an exemplaryembodiment, the power supply can be connected to the processor 780 viathe power management system, and thus use the power management system tomanage charging, discharging, and/or power management functions. Thepower supply 790 may also include one or more DC or AC power supplies, arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator and/or any other suitablecomponents.

Although not shown in FIG. 7, the terminal 700 can further include acamera, a Bluetooth module, etc. without limitation. Specifically, theterminal can have a displaying unit of a touch screen display, a memory,and one or more programs stored in the memory. The terminal can beconfigured to use one or more processor to execute the one or moreprograms stored in the memory.

For example, the processor 780 can at least be configured to obtainaudio data to be transmitted; to encode the obtained audio dataaccording to the M-bit unit length. The M-bit unit length is an encodinglength corresponding to each frequency of a number N of frequencies, Nis greater than or equal to 2, and M is greater than 0.

For example, the processor 780 can be configured to use the pre-setcross-platform audio interface to control the audio outputting device ofthe sending end to send the encoded audio data to other one or moreterminal devices, such that the other one or more terminal devices usethe pre-set cross-platform audio interface to control the audioinputting device of the receiving end to receive the encoded audio data.

In addition, when encoding the obtained audio data according to theM-bit unit length, the processor 780 of the terminal device can beconfigured to select the number N of frequencies in a transmittableaudio frequency domain. Each frequency of the number N of frequenciescorresponds to an M-bit encode, N is greater than or equal to 2, and Mis greater than 0. The processor 780 of the terminal device can also beconfigured to append a different tag respectively at a start positionand an end position of the obtained audio data. The different tag caninclude the encode corresponding to any frequency of the number N offrequencies. The processor 780 of the terminal device can further beconfigured to use the third-party library to perform the errorcorrection to the audio data having the appended tags, and to encode theaudio data after the error correction according to the M-bit unitlength.

Further, when controlling the audio outputting device 761 of the sendingend and sending the encoded audio data to other terminal devices, theprocessor 780 of the terminal device can be configured to obtaininformation of other terminal devices via the pre-set cross-platformaudio interface; to use the audio outputting device 761 to send current,encoded audio data to the other terminal devices, according to theobtained information of the other terminal devices; and/or to use thecallback function of the cross-platform audio interface to detectwhether new, encoded audio data exist after finishing sending thecurrent, encoded audio data. When detecting that the new, encoded audiodata exist, the processor 780 of the terminal device can be configuredto continuously use the audio outputting device 761 to send the new,encoded audio data. When the new, encoded audio data do not exist, theprocessor 780 of the terminal device can be configured to stop sendingthe new, encoded audio data.

In addition, when controlling the audio inputting device 762 of thereceiving end to receive the encoded audio data via the pre-setcross-platform audio interface, the processor 780 of the terminal devicecan further be configured to use the pre-set cross-platform audiointerface to create a new thread; to use the new thread to control theaudio inputting device 762 to receive the encoded audio data, theencoded audio data including the audio data having the appended tags atthe start position and the end position; to convert the received audiodata into an audio signal via fast Fourier transform; to restore theaudio signal to a digital signal according to a digital frequencyencoding table; and/or to use the third-party library to decode thedigital signal and to obtain the audio data to be transmitted.

In this manner, the disclosed information transmission can only useaudio outputting devices (e.g., a speaker) already-equipped in a sendingunit and audio inputting devices (e.g., microphone) already-equipped ina receiving unit to achieve information transmission via an encodingmode. There is no need for additional hardware devices. Further, duringthe information transmission, there is no need to match or pair the twotransmitting parties before the transmission. Moreover, the sending (ortransmitting) end can send information simultaneously to one or morereceiving ends to improve transmission efficiency.

It should be noted that, in the present disclosure each embodiment isprogressively described, i.e., each embodiment is described and focusedon difference between embodiments. Similar and/or the same portionsbetween various embodiments can be referred to with each other. Inaddition, exemplary apparatus is described with respect to correspondingmethods.

Note that, the term “comprising”, “including” or any other variantsthereof are intended to cover a non-exclusive inclusion, such that theprocess, method, article, or apparatus containing a number of elementsalso include not only those elements, but also other elements that arenot expressly listed; or further include inherent elements of theprocess, method, article or apparatus. Without further restrictions, thestatement “includes a” does not exclude other elements included in theprocess, method, article, or apparatus having those elements.

A person of ordinary skill in the art can understand that the modulesincluded herein are described according to their functional logic, butare not limited to the above descriptions as long as the modules canimplement corresponding functions. Further, the specific name of eachfunctional module is used for distinguishing from on another withoutlimiting the protection scope of the present disclosure.

In various embodiments, the disclosed modules can be configured in oneapparatus or configured in multiple apparatus as desired. The modulesdisclosed herein can be integrated in one module or in multiple modules.Each of the modules disclosed herein can be divided into one or moresub-modules, which can be recombined in any manner.

One of ordinary skill in the art would appreciate that suitable softwareand/or hardware (e.g., a universal hardware platform) may be includedand used in the disclosed methods and systems. For example, thedisclosed embodiments can be implemented by hardware only, whichalternatively can be implemented by software products only. The softwareproducts can be stored in a computer-readable storage medium (e.g., asshown in FIG. 14) including, e.g., ROM/RAM, magnetic disk, optical disk,etc. The software products can include suitable commands to enable aterminal device (e.g., including a mobile phone, a personal computer, ora network device, etc.) to implement the disclosed embodiments.

The embodiments disclosed herein are exemplary only. Other applications,advantages, alternations, modifications, or equivalents to the disclosedembodiments are obvious to those skilled in the art and are intended tobe encompassed within the scope of the present disclosure.

INDUSTRIAL APPLICABILITY AND ADVANTAGEOUS EFFECTS

Without limiting the scope of any claim and/or the specification,examples of industrial applicability and certain advantageous effects ofthe disclosed embodiments are listed for illustrative purposes. Variousalternations, modifications, or equivalents to the technical solutionsof the disclosed embodiments can be obvious to those skilled in the artand can be included in this disclosure.

Methods, systems, and terminal devices for transmitting information areprovided. An exemplary system includes a sending end and at least onereceiving end. The sending end is configured to obtain audio data to betransmitted, encode the obtained audio data according to an M-bit unitlength, and use a pre-set cross-platform audio interface to control anaudio outputting device of the sending end to send the encoded audiodata to the at least one receiving end. The M-bit unit length is anencoding length corresponding to each frequency of a number N offrequencies, N is greater than or equal to 2, and M is greater than 0.The at least one receiving end is configured to use the pre-setcross-platform audio interface to control an audio inputting device ofthe at least one receiving end to receive the encoded audio data.

As disclosed, a cross-platform audio interface can be configured and canbe used to block/remove differences among information transmittingplatforms of various terminal devices. Unitive standards can be used torealize information transmitting between different terminal devices.

The disclosed methods, systems, and terminal devices for transmittinginformation can only use audio outputting devices (e.g., a speaker)already-equipped in a sending unit and audio inputting devices (e.g.,microphone) already-equipped in a receiving unit to achieve informationtransmission via an encoding mode. There is no need for additionalhardware devices. Further, during information transmission, there is noneed to match or pair transmitting parties before the transmission.Moreover, the sending (or transmitting) end can send informationsimultaneously to one or more receiving ends to improve transmissionefficiency.

What is claimed is:
 1. An information transmitting method implemented bya system including a sending end and at least one receiving end,comprising: obtaining, by the sending end, audio data to be transmitted;coding, by the sending end, the obtained audio data according to anM-bit unit length, wherein the M-bit unit length is an encoding lengthcorresponding to each frequency of a number N of frequencies, the Nfrequencies being in a transmittable audio frequency range, N is greaterthan or equal to 2, and M is greater than 0; using, by the sending end,a pre-set cross-platform audio interface to control an audio outputtingdevice of the sending end to send the encoded audio data to the at leastone receiving end, the audio outputting device being a speaker; andusing, by the at least one receiving end, the pre-set cross-platformaudio interface to control an audio inputting device of the at least onereceiving end to receive the encoded audio data, the audio inputtingdevice being a microphone; wherein the sending end sends the encodedaudio data to the at least one receiving end via acoustic communication.2. The method according to claim 1, wherein encoding the obtained audiodata according to the M-bit unit length includes: selecting the number Nof frequencies in the transmittable audio frequency range, wherein eachfrequency of the number N of frequencies corresponds to an M-bit encode;appending respectively, a first tag at a start position of the obtainedaudio data and a second tag at an end position of the obtained audiodata, wherein the first tag includes an encode corresponding to a firstfrequency of the number N of frequencies, and the second tag includes anencode corresponding to a second frequency of the number N offrequencies; and using a third-party library to perform an errorcorrection to the audio data having the appended tags, and encoding theaudio data after the error correction according to the M-bit unitlength.
 3. The method according to claim 1, wherein controlling theaudio outputting device and sending the encoded audio data includes:obtaining information of the at least one receiving end via the pre-setcross-platform audio interface by the sending end; using the audiooutputting device of the sending end to send current, encoded audio datato the at least one receiving end, according to the obtained informationof the at least one receiving end; after finishing sending the current,encoded audio data, using a callback function of the cross-platformaudio interface to detect whether new, encoded audio data exist; andwhen detecting that the new, encoded audio data exist, continuouslyusing the audio outputting device of the sending end to send the new,encoded audio data; or when the new, encoded audio data do not exist,stopping sending the new, encoded audio data.
 4. The method according toclaim 1, wherein controlling the audio inputting device of the receivingend to receive the encoded audio data via the pre-set cross-platformaudio interface by the at least one receiving end includes: using thepre-set cross-platform audio interface to create a new thread by the atleast one receiving end; using the new thread to control the audioinputting device of the receiving end to receive the encoded audio data,wherein the encoded audio data include the audio data having theappended tags at the start position and the end position; converting thereceived audio data into an audio signal via fast Fourier transform;restoring the audio signal to a digital signal according to a digitalfrequency encoding table; and using the third-party library to decodethe digital signal and to obtain the audio data to be transmitted.
 5. Aninformation transmitting method, comprising: obtaining audio data to betransmitted by a sending end containing an audio outputting device, theaudio outputting device being a speaker; coding the obtained audio dataaccording to an M-bit unit length, wherein the M-bit unit length is anencoding length corresponding to each frequency of a number N offrequencies, the N frequencies being in a transmittable audio frequencyrange, wherein N is greater than or equal to 2, and M is greater than 0;and using a pre-set cross-platform audio interface to control the audiooutputting device of the sending end to send the encoded audio data toat least one receiving end, such that the at least one receiving enduses the pre-set cross-platform audio interface to control an audioinputting device at the at least one receiving end to receive theencoded audio data, the audio inputting device being a microphone;wherein the sending end sends the encoded audio data to the at least onereceiving end via acoustic communication.
 6. The method according toclaim 5, wherein encoding the obtained audio data according to the M-bitunit length includes: selecting the number N of frequencies in thetransmittable audio frequency range, wherein each frequency of thenumber N of frequencies corresponds to an M-bit encode; appendingrespectively, a first tag at a start position of the obtained audio dataand a second tag at an end position of the obtained audio data, whereinthe first tag includes an encode corresponding to a first frequency ofthe number N of frequencies, and the second tag includes an encodecorresponding to a second frequency of the number N of frequencies; andusing a third-party library to perform an error correction to the audiodata having the appended tags, and encoding the audio data after errorcorrection according to the M-bit unit length.
 7. The method accordingto claim 5, wherein controlling the audio outputting device and sendingthe encoded audio data includes: obtaining information of the at leastone receiving end via the pre-set cross-platform audio interface; usingthe audio outputting device to send current, encoded audio data to theat least one receiving end according to the obtained information of theat least one receiving end; after finishing sending the current, encodedaudio data, using a callback function of the cross-platform audiointerface to detect whether new, encoded audio data exist; and whendetecting that the new encoded audio data exist, continuously using theaudio outputting device of the sending end to send the new, encodedaudio data; or when the new encoded audio data do not exist, stoppingsending the new, encoded audio data.
 8. The method according to claim 5,the sending end being connected to a receiving end containing an audioinputting device, the method further comprising: using a pre-setcross-platform audio interface to control the audio inputting device ofthe receiving end to receive encoded audio data sent from the sendingend by a process comprising: using the pre-set cross-platform audiointerface to create a new thread; using the new thread to control theaudio inputting device of the receiving end to receive the encoded audiodata, wherein the encoded audio data include audio data having appendedtags at a start position and an end position of the audio data;converting the received audio data into an audio signal via fast Fouriertransform; restoring the audio signal to a digital signal according to adigital frequency encoding table; and using the third-party library todecode the digital signal and to obtain audio data to be transmitted. 9.The method according to claim 1, wherein: the audio outputting device iswithin a sound collecting range of the audio inputting device.
 10. Themethod according to claim 1, wherein M and N are integers, and N issmaller or equal to 2^(m).
 11. The method according to claim 1, wherein:the obtained audio data to be transmitted includes audio data convertedfrom text messages at the sending end.
 12. An information transmittingsystem comprising: a sending end and at least one receiving end, thesending end containing an audio outputting device and the at least onereceiving end containing an audio inputting device, the audio outputtingdevice being a speaker and the audio inputting device being amicrophone, wherein: the sending end is configured to obtain audio datato be transmitted, to encode the obtained audio data according to anM-bit unit length, and to use a pre-set cross-platform audio interfaceto control the audio outputting device to send the encoded audio data tothe at least one receiving end, wherein the M-bit unit length is anencoding length corresponding to each frequency of a number N offrequencies, the N frequencies being in a transmittable audio frequencyrange, N is greater than or equal to 2, and M is greater than 0; and theat least one receiving end is configured to use the pre-setcross-platform audio interface to control the audio inputting device ofthe at least one receiving end to receive the encoded audio data;wherein the sending end sends the encoded audio data to the at least onereceiving end via acoustic communication.
 13. The system according toclaim 12, wherein the sending end is configured to: select the number Nof frequencies in the transmittable audio frequency range, wherein eachfrequency of the number N of frequencies corresponds to an M-bit encode;append respectively, a first tag at a start position of the obtainedaudio data and a second tag at an end position of the obtained audiodata, wherein the first tag includes an encode corresponding to a firstfrequency of the number N of frequencies, and the second tag includes anencode corresponding to a second frequency of the number N offrequencies; and use a third-party library to perform an errorcorrection to the audio data having the appended tags, and to encode theaudio data after the error correction according to the M-bit unitlength.
 14. The system according to claim 12, wherein the sending end isconfigured to: use the pre-set cross-platform audio interface to obtaininformation of the at least one receiving end; use the audio outputtingdevice of the sending end to send current, encoded audio data to the atleast one receiving end, according to the obtained information of the atleast one receiving end; after finishing sending the current, encodedaudio data, use a callback function of the cross-platform audiointerface to detect whether new, encoded audio data exist; and whendetecting that a new, encoded audio data exist, continuously use theaudio outputting device of the sending end to send the new, encodedaudio data; or when the new, encoded audio data do not exist, stopsending the new, encoded audio data.
 15. The system according to claim12, wherein the at least one receiving end is configured to: use thepre-set cross-platform audio interface to create a new thread; use thenew thread to control the audio inputting device of the receiving end toreceive the encoded audio data, wherein the encoded audio data includethe audio data having the appended tags at the start position and theend position; convert the received audio data into an audio signal viafast Fourier transform; restore the audio signal to a digital signalaccording to a digital frequency encoding schedule; and use thethird-party library to decode the digital signal and to obtain the audiodata to be transmitted.
 16. A terminal device containing an audiooutputting device comprising: a data obtaining unit configured to obtainaudio data to be transmitted; a data encoding unit configured to encodethe obtained audio data according to an M-bit unit length, wherein theM-bit unit length is an encoding length corresponding to each frequencyof a number N of frequencies, the N frequencies being in a transmittableaudio frequency range, N is greater than or equal to 2, and M is greaterthan 0; and a data sending unit configured to use a pre-setcross-platform audio interface to control the audio outputting device ofthe sending end to send the encoded audio data to at least one receivingend, such that the at least one receiving end uses the pre-setcross-platform audio interface to control the audio inputting device atthe at least one receiving end to receive the encoded audio data, theaudio outputting device being a speaker and the audio inputting devicebeing a microphone; wherein the sending end sends the encoded audio datato the at least one receiving end via acoustic communication.
 17. Theterminal device according to claim 16, wherein the data encoding unitincludes: a frequency selecting module configured to select the number Nof frequencies in the transmittable audio frequency range, wherein eachfrequency of the number N of frequencies corresponds to an M-bit encode;a tag appending module configured to append respectively, a first tag ata start position of the obtained audio data and a second tag at an endposition of the obtained audio data, wherein the first tag includes anencode corresponding to a first frequency of the number N offrequencies, and the second tag includes an encode corresponding to asecond frequency of the number N of frequencies; and a data encodingmodule configured to use a third-party library to perform an errorcorrection to the audio data having the appended tags, and encoding theaudio data after error correction according to the M-bit unit length.18. The terminal device according to claim 16, wherein the data sendingunit includes: an information obtaining module configured to obtaininformation of the at least one receiving end via the pre-setcross-platform audio interface; a data sending module configured to usethe audio outputting device to send current, encoded audio data to theat least one receiving end according to the obtained information of theat least one receiving end; a detecting module configured, afterfinishing sending the current, encoded audio data, to use a callbackfunction of the cross-platform audio interface to detect whether new,encoded audio data exist; and a processing module configured, whendetecting that the new encoded audio data exist, to continuously use theaudio outputting device of the sending end to send the new, encodedaudio data; or when the new encoded audio data do not exist, to stopsending the new, encoded audio data.
 19. The terminal device accordingto claim 16, further comprising: an audio inputting device; and a datareceiving unit configured to use a pre-set cross-platform audiointerface to control the audio inputting device of the receiving end toreceive encoded audio data sent from the audio outputting device of thesending end.
 20. The terminal device according to claim 19, wherein thedata receiving unit includes: a thread creating module configured to usethe pre-set cross-platform audio interface to create a new thread; adata receiving module configured to use the new thread to control theaudio inputting device of the receiving end to receive the encoded audiodata, wherein the encoded audio data include audio data having appendedtags at a start position and an end position of the audio data; aconverting module configured to convert the received audio data into anaudio signal via fast Fourier transform; a restoring module configuredto restore the audio signal to a digital signal according to a digitalfrequency encoding table; and a data obtaining module configured to usethe third-party library to decode the digital signal and to obtain audiodata to be transmitted.